Physical uplink control channel resource determination and multiplexing of multiple hybrid automatic repeat request acknowledgement feedbacks and other uplink control information on physical uplink control channel and physical uplink shared channel

ABSTRACT

A device of a New Radio (NR) User Equipment (UE), a method and a machine readable medium to implement the method. The device includes a Radio Frequency (RF) interface, and processing circuitry coupled to the RF interface, the processing circuitry to: determine that the UE is configured with a feature of multiple Physical Uplink Control Channel (PUCCH) resources with HARQ-ACK feedback within a slot; determine a Physical Uplink Control Channel (PUCCH) resource to carry Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback in response to a scheduled Physical Downlink Shared Channel (PDSCH) resource; and encode for transmission to a NR evolved NodeB (gNodeB) the PUCCH resource, the PUCCH resource to carry the HARQ-ACK feedback and: another PUCCH resource carrying Uplink Control Information (UCI) other than HARQ-ACK feedback, and a scheduled Physical Uplink Shared Channel (PUSCH) resource.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/739,081 entitled “MULTIPLEXING OFMULTIPLE HARQ-ACK FEEDBACKS AND OTHER UCI ON PUCCH AND PUSCH,” filedSep. 28, 2018, the entire disclosure of which are incorporated herein byreference.

FIELD

Various embodiments generally may relate to the field of wirelesscommunications, and particularly to the field of Hybrid Automatic RepeatRequest Acknowledgment scheduling using uplink resources in a cellularnetwork environment.

BACKGROUND

Current Third Generation Partnership Project (3GPP) New Radio (NR)specifications do not specifically address issues related to the mannerof multiplexing uplink resources, such as UCI carrying HARQ-ACKfeedback.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates time frequency resources showing a multiplexing ofHARQ-ACK feedback with another Uplink Control Information (UCI) in aPhysical Uplink Control Channel (PUCCH) resource in a single slotaccording to a first embodiment;

FIG. 2 illustrates time frequency resources showing a multiplexing ofHARQ-ACK feedback with another UCI in a PUCCH resource in a single slotaccording to a second embodiment;

FIG. 3 illustrates a PUCCH resource carrying different types of HARQ-ACKfeedback according to one embodiment;

FIG. 4 illustrates time frequency resources showing a multiplexing ofHARQ-ACK feedback with a Physical Uplink Shared Channel (PUSCH) resourceaccording to one embodiment;

FIG. 5 illustrates a process according to an embodiment;

FIG. 6 illustrates an architecture of a system of a network according tosome embodiments; and

FIG. 7 illustrates example interfaces of baseband circuitry according tovarious embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects ofvarious embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the various embodiments may be practiced in other examplesthat depart from these specific details. In certain instances,descriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description of the various embodiments withunnecessary detail. For the purposes of the present document, the phrase“A or B” means (A), (B), or (A and B).

Mobile communication has evolved significantly from early voice systemsto today's highly sophisticated integrated communication platforms. Thenext generation wireless communication system, 5G, or new radio (NR),will provide access to information and sharing of data anywhere, anytimeby various users and applications.

As defined in NR, short physical uplink control channel (PUCCH) (PUCCHformats 0 and 2) can span 1 or 2 symbols and long PUCCH (PUCCH formats1, 3 and 4) can span from 4 to 14 symbols within a slot. Further, longPUCCH may span multiple slots to further enhance coverage. In addition,for a given User Equipment (UE), two short PUCCHs as well as short PUCCHand long PUCCH can be multiplexed in a time division multiplexing (TDM)manner in the same slot.

In NR, uplink control information (UCI) can be carried by PUCCH orPUSCH. In particular, UCI may include scheduling request (SR), hybridautomatic repeat request-acknowledgement (HARQ-ACK) feedback, channelstate information (CSI) report, e.g., channel quality indicator (CQI),pre-coding matrix indicator (PMI), CSI resource indicator (CRI) and rankindicator (RI) and/or beam related information (e.g., L1-RSRP (layer1-reference signal received power)).

In NR Release 15 (Rel-15), it was agreed that for semi-static anddynamic hybrid automatic repeat request-acknowledgement (HARQ-ACK)codebook, only one HARQ-ACK feedback is to be transmitted in one slot.Further, this HARQ-ACK feedback can be carried by either physical uplinkcontrol channel (PUCCH) or physical uplink shared channel (PUSCH).Further, for semi-static and dynamic HARQ-ACK codebook in a singlecomponent carrier (CC) scenario, PUCCH resource allocation is determinedin accordance with the last downlink control information (DCI)scheduling the physical downlink shared channel (PDSCH). In particular,a PUCCH resource indicator in the last DCI and/or a starting controlchannel element (CCE) index for the physical downlink control channel(PDCCH) carrying the last DCI are jointly employed to determine thePUCCH resource carrying HARQ-ACK feedback.

As mentioned above, only one HARQ-ACK feedback or PUCCH/PUSCHtransmission carrying HARQ-ACK feedback is allowed in a slot in the NRRel-15 specification. In the event that the PUCCH carrying HARQ-ACKfeedback is scheduled in the last part of the slot, a HARQ-ACK feedbackdelay can be expected, especially when considering the smallersubcarrier spacing, e.g., 15 kHz including a 1 ms slot duration. Tosupport Ultra Reliable Low Latency Communication (URLLC) types ofapplications, it is envisioned according to embodiments that anadditional PUCCH resource carrying HARQ-ACK feedback in a slot may beneeded. For instance, the additional PUCCH resource carrying HARQ-ACKfeedback may be transmitted in the earlier part of the slot so as toreduce latency.

Where plurality of PUCCH resources carrying HARQ-ACK feedback areenvisioned to be scheduled in a slot, however, the plurality of PUCCHresources may overlap with another PUCCH resource carrying a same ordifferent UCI types or carrying PUSCH. In such a case, certainmechanisms are needed for UCI multiplexing to ensure alignment between aNR evolved NodeB (gNodeB) and a UE.

Embodiments pertain to devices, methods, systems and products to allowmultiplexing of multiple HARQ-ACK feedbacks and other UCI on PUCCH andPUSCH in a same slot. In particular, embodiments envision multiplexingmultiple HARQ-ACK feedbacks and other UCI on PUCCH, and multiplexingmultiple HARQ-ACK feedbacks and PUSCH

Multiplexing Multiple HARQ-ACK Feedbacks and Other UCI on PUCCH

As mentioned above, in case a plurality of PUCCH resources carryingHARQ-ACK feedback are scheduled in a slot, and the plurality of PUCCHresources overlap with another PUCCH carrying a same or different UCItypes or PUSCH, certain mechanisms need to be defined for UCImultiplexing.

In the following description, dynamic HARQ-ACK feedback corresponds tothe case where the HARQ-ACK is in response to a physical downlink sharedchannel (PDSCH) reception scheduled by a corresponding physical downlinkcontrol channel (PDCCH). In addition, semi-persistent scheduled (SPS)HARQ-ACK feedback corresponds to the case where the HARQ-ACK is inresponse to a PDSCH reception without an associated PDCCH.

Embodiments of multiplexing multiple HARQ-ACK feedback and other UCI onPUCCH in a slot are described below.

According to one embodiment, when a plurality of PUCCH resourcescarrying dynamic HARQ-ACK feedback in a first UCI overlap with anotherPUCCH resource carrying a second UCI, wherein HARQ-ACK feedback and thesecond UCI are not distinguished in terms of the corresponding servicetypes or priorities, and if a timeline requirement is satisfied, the UCImultiplexing follows the procedure as defined in Section 9.2.5 inTS38.213 V15.2.0.

The second UCI may include a periodic and/or semi-persistent scheduledCSI (P/SP-CSI) report and/or SR and/or SPS HARQ-ACK feedback. Further,it is assumed here that the UE is configured to multiplex HARQ-ACK andCSI in a PUCCH resource via higher layers. Otherwise, the UE is expectedto transmit the PUCCH transmissions with the HARQ-ACK feedback and todrop the P/SP-CSI reports.

More specifically, according to some embodiments, in a first step, theUE may determine a set of overlapping PUCCH resources for UCImultiplexing. In NR Rel-15, for PUCCH resource allocation, the resourceset is first determined based on the UCI payload size. Within a resourceset, one resource from multiple configured resources are indicated toUE, based on the PUCCH resource indicator field in DCI. Each PUCCHresource is identified by PUCCH format, starting symbol, starting RB(frequency-domain allocation), cyclic shifts, and code domain allocation(e.g., if there is an OCC, etc., depending on the particular format).This information can therefore be indicated to the UE.

When the second UCI and the first HARQ-ACK PUCCH resource are consideredfor UCI multiplexing, if the resulting determined first PUCCH resourcecarrying the second UCI and the first HARQ-ACK feedback do not overlapwith the second HARQ-ACK PUCCH resource, and if one of the PUCCHresources is a short PUCCH, the UE may transmit two PUCCHs in a slot.Alternatively, the second UCI and the second HARQ-ACK payload may beconsidered for UCI multiplexing, and if the resulting determined secondPUCCH resource carrying the second UCI and the second HARQ-ACK feedbackpayload do not overlap with the first HARQ-ACK PUCCH resource, and ifone of the PUCCH resources is a short PUCCH, then the UE may transmitthe first HARQ-ACK PUCCH and the determined second PUCCH resource withinthe slot.

As a generalization of the above, the UE may evaluate either option ofmultiplexing the second UCI with the first or the second HARQ-ACK PUCCHresource, and may transmit the combination of multiple PUCCHtransmissions within the slot depending on the resulting determinedfirst PUCCH resource (to carry the first HARQ-ACK feedback and thesecond UCI) or the second PUCCH resource (to carry the second HARQ-ACKand the second UCI). In case both options are feasible, the UE maytransmit following either the (i) updated/determined first PUCCHresource and second HARQ-ACK PUCCH, or the (ii) updated/determinedsecond PUCCH resource and first HARQ-ACK PUCCH. The first or secondPUCCH resources are “updated” as used herein in the sense that they areused to multiplex the first or second HARQ-ACK feedback with the secondUCI, respectively.

FIG. 1 illustrates one example of multiplexing two HARQ-ACKs and asecond UCI (such as one carrying P/SP-CSI reports) on PUCCH in a slot104 with symbols 102. In particular, FIG. 1 shows respective timefrequency resources 100 a and 100 b, where resource 100 a showsdetermined uplink resources prior to multiplexing of a first or secondHARQ-ACK feedback with the second UCI, and resource 100B shows uplinkresources updated after multiplexing of the first HARQ-ACK feedback withthe second UCI according to one embodiment (updated uplink resources).In particular, in the example, as shown in FIG. 1 at 100 a, two PUCCHresources 106 a and 110 a to carry separate first and second HARQ-ACKfeedbacks, respectively, are determined by the UE to overlap withanother PUCCH resource 108 a that is to carry P/SP CSI report. Accordingto the UCI multiplexing procedure of one embodiment, uplink resourcesmay be updated by the UE in the form of PUCCH resource 106 b to carrythe second UCI of PUCCH resource 108 a along with the first HARQ-ACKfeedback of PUCCH resource 106 a. Given that the determined first PUCCHresource 106 a does not overlap with the second determined HARQ-ACKPUCCH resource 110 a in FIG. 1, the UE may therefore, according to thisembodiment, transmit both updated PUCCH resources 106 b and 108 b in asame slot 104 as shown in FIG. 1.

By allowing multiple HARQ-ACKs to be transmitted within a slot, a PUCCHresource indicator in the DC's scheduling the PDSCHs where thecorresponding HARQ-ACK feedbacks are scheduled in the same slot, may,according to an embodiment, point to different starting symbols forPUCCH resources, or to different PUCCH resources with no time domainoverlap. The actual PUCCH resources which carry such feedbacks (as wellas other potentially multiplexed reports), may then be determineddirectly based on the corresponding PUCCH resource indicator values.This is applicable both for the case where HARQ-ACK feedbacks do notoverlap with each other or any other report/information, as well as whenany HARQ-ACK feedback overlaps (and is multiplexed) with any otherreports/information, while the resulting determined PUCCH resource doesnot overlap with other HARQ-ACK feedbacks (or HARQ-ACK feedbacksmultiplexed with some other reports/information).

With the PUCCH resource indicator values being read and used from thecorresponding DCIs, some reference point may be defined to furtheradjust the PUCCH resource, such as, for example, its starting symbol. Inone example, the PUCCH resource indicator may be interpreted relative tothe beginning of the slot. In another example, the PUCCH resourceindicator may be interpreted relative to the end/start of the last PUCCHresource carrying a HARQ-ACK.

Alternatively, some relative symbol offset may be defined anddynamically or semi-statically indicated by RRC configuration signalingor L1-signaling, such that in case of multiple HARQ-ACK transmissionswithin a slot, the timing relationship between the corresponding PUCCHresources carrying the HARQ-ACK feedbacks (potentially each multiplexedwith any other report/information), are implicitly or explicitlyindicated to the UE.

According to one embodiment, the indication of different PUCCH resourcesfor HARQ-ACK feedback within a slot may be achieved via a combination ofa K1 offset (as indicated by a PDSCH-to-HARQ-timing-indicator field inthe scheduling DCI format, if present, or as provided by higher layerparameter dl-DataToUL-ACK) and the PUCCH resource indicator (PRI) in thescheduling DCI. Specifically, the starting symbol of a PUCCH resourceindicated by the PRI may be interpreted jointly with the indicated valueof the PDSCH-to-HARQ-timing-indicator field K1 in the DCI (or asprovided by the higher layer parameter dl-DataToUL-ACK), wherein thelatter indication may be reinterpreted to indicate the PDSCH-end to theHARQ-ACK-start timing offset using a combination of one or more of:slots, half-slots, or a set of one or more symbols (as against theRel-15 interpretation in terms of number of slots).

According to an embodiment, the UE may be configured by higher layers(such as by UE-specific RRC signaling) with the possibility of multiplePUCCH transmissions with HARQ-ACK feedback in a slot, or alternatively,configured by higher layers to follow a different interpretation of theK1 offset and PUCCH resource starting symbol determination for HARQ-ACKfeedback while being capable of transmitting multiple PUCCHtransmissions with HARQ-ACK feedback in a slot.

Following the above, the value indicated usingPDSCH-to-HARQ-timing-indicator field in the DCI format (and/or thehigher layer parameter dl-DataToUL-ACK) may be interpreted in units ofhalf-slots or in units of a specified number of one or more symbols,e.g., 2, 4 or 7 symbols. Subsequently, the startingSymbolIndex parameteris interpreted with respect to the half-slot boundary as against theslot boundary with the value of the starting PUCCH symbol translated asstartingSymbolIndex′=(startingSymbolIndex−7) (and asstartingSymbolIndex′=(startingSymbolIndex−6) for ECP case).

According to some other embodiments, let us assume that thePDSCH-to-HARQ-timing-indicator field in the DCI format is either N=2 or3 bits long. In such a case, the PDSCH-to-HARQ-timing-indicator field inthe DCI format may be interpreted such that the last (N−1) leastsignificant bit(s) (LSBs) of the DCI bit-field indicate one of 2 (N−1)values in units of slots as configured in the first 2 (N−1) valuesprovided by higher layer parameter dl-DataToUL-ACK, and the mostsignificant bit (MSB) (1 bit) of the PDSCH-to-HARQ-timing-indicatorfield in the DCI format is used to indicate an additional half-slotoffset or a symbol group, where the number of symbols within the symbolgroup can be predefined in the specification or configured by higherlayers. Thus, for the half-slot offset indication, a ‘0’ may indicatethat the timing offset is in terms of an integer number of slots fromPDSCH-end, while a ‘1’ indicates that the timing offset is in terms ofan integer number of slots from the PDSCH-end plus another half-slot (7symbols for normal cyclic prefix (NCP) length and 6 symbols for extendedcyclic prefix (ECP) length where the cyclic prefix (CP) configurationcorresponds to that for the PUCCH in the corresponding UL bandwidth part(BWP)). Further, when an additional half-slot offset is indicated, thenthe UE interprets the starting symbol for the indicated PUCCH resourcewith respect to symbol index 7 (for NCP) or symbol index 6 (for ECP) ofthe corresponding slot. Accordingly, the parameter startingSymbolIndexof the PUCCH resource is translated asstartingSymbolIndex′=(startingSymbolIndex−7) (and asstartingSymbolIndex′=(startingSymbolIndex−6) for ECP case).

For the case when the PDSCH-to-HARQ-timing-indicator field in the DCIformat is N=1 bit-long, the bit-field may only indicate the whether ornot to apply a half-slot offset in addition to the timing offsetindicated by the first value indicated by the higher layer parameterdl-DataToUL-ACK. This mechanism can be extended to other variants usingindication of the PDSCH to HARQ-ACK timing offset in units of ‘k’symbols with value of ‘k’ other than 7 (or 6 for the ECP case). Anadvantage of the above mechanism is that the grouping of HARQ-ACKfeedback to multiple PUCCH resources within a slot is realized byindicating this information using part of the slot offset indicationinstead of using additional DCI bits or alternative mechanisms, e.g.,partitioning of PUCCH resource sets or partitioning of HARQ processes orbased on RNTI.

In another embodiment, the PUCCH resource information corresponding tothe PUCCH resources carrying multiple HARQ-ACK feedbacks, e.g., PUCCHformats, starting symbols, starting RBs (frequency-domain allocation),cyclic shifts, and code domain allocations, may be configured by ajointly encoded time domain resource allocation (TD-RA) table anddynamic indication of a combination of such parameters to the UE.

Referring back to the embodiment shown in FIG. 1, in case theupdated/determined first PUCCH resource carrying the second UCI and thefirst HARQ-ACK feedback overlaps with the updated/determined secondHARQ-ACK PUCCH resource (not shown), or if the second UCI and twonon-overlapping HARQ-ACK PUCCH resources (as shown in FIG. 1) areconsidered for UCI multiplexing, and if the DCI format scheduling thesecond PDSCH is detected at least N₃ symbols before the first symbol ofthe first HARQ-ACK feedback resource (where N₃ is, for example, definedas “Capability #1” or “Capability #2” in Table 1 below), the UE may,according to an embodiment, multiplex all UCI including multipleHARQ-ACK feedbacks and the second UCI into one PUCCH resource, where ρdesignates the subcarrier spacing SCS by way of the equation: Δ=2μ×15where Δ corresponds to the SCS expressed in kHz.

TABLE 1 N3 values for different SCS (μ) and UE minimum processing timecapabilities μ Capability #1 Capability #2 0 8 3 1 10 4.5 2 17 9 3 20N/A

FIG. 2 illustrates one example of multiplexing two HARQ-ACKs andP/SP-CSI reports on PUCCH.

In particular, FIG. 2 shows respective time frequency resources 200 aand 200 b in symbols 202 of a slot 204, where resource 200 a showsdetermined uplink resources prior to multiplexing of a first and secondHARQ-ACK feedback with the second UCI, and resource 200 b shows uplinkresources updated after multiplexing of the first and second HARQ-ACKfeedbacks with the second UCI according to one embodiment (updateduplink resources). In particular, in the example, as shown in FIG. 2,two PUCCH resources 206 a and 210 a to carry separate first and secondHARQ-ACK feedbacks, respectively, are determined by the UE to overlapwith another PUCCH 208 a that is to carry P/SP CSI report. According tothe UCI multiplexing procedure of one embodiment, uplink resources maybe updated by the UE in the form of PUCCH 206 b to carry the second UCIof PUCCH resource 208 a along with the first and second HARQ-ACKfeedbacks of PUCCH resource 206 a. Given that the determined first PUCCHresource 206 a does not overlap with the second determined HARQ-ACKPUCCH resource 210 a in FIG. 2, the UE may therefore, according to thisembodiment, transmit updated PUCCHs 206 b carrying all UCIs in a sameslot 204 as shown in FIG. 2. The PUCCH resource 206 b may be determinedbased on the PRI field which is used to indicate the PUCCH carrying thefirst HARQ-ACK feedback.

According to one embodiment, when multiple HARQ-ACKs are multiplexed inone PUCCH resource (potentially multiplexed with any other ULreport/information), the PUCCH resource carrying combined UCI may bedetermined in accordance with PUCCH resource indicator (PRI) which isused to indicate the PUCCH carrying the first or the last dynamicHARQ-ACK feedback among multiple HARQ-ACK feedbacks. More specifically,one PUCCH resource set may be determined based on the total payload sizeof the combined UCI. Further, the aforementioned PRI may be used toallow selection of one PUCCH resource from the determined PUCCH resourceset.

Alternatively, the PUCCH resource carrying combined UCI may bedetermined in accordance with PUCCH resource indicator (PRI) which isincluded in the first or last DCI scheduling the PDSCHs where thecorresponding HARQ-ACK feedbacks are scheduled in the same slot. In thecase of carrier aggregation, the PRI may be included in the DCI which istransmitted with the lowest component carrier (CC) index.

According to one embodiment, the bit order of HARQ-ACK feedbacks withinthe combined UCI may follow the timing of one or more of: first symbolof each HARQ-ACK feedback in the same slot, the relative timing betweenthe PDCCH monitoring occasions in which the corresponding schedulingDC's are detected, and the relative timing between the first or lastsymbol of the scheduled PDSCHs. For instance, assuming N HARQ-ACKfeedbacks are scheduled in the same slot, the bit order of HARQ-ACKfeedbacks within the combined UCI can be 1^(st) HARQ-ACK, 2^(nd)HARQ-ACK, . . . , N^(th) HARQ-ACK. Alternatively, the ordering of theHARQ-ACK feedback information may be determined according to the orderof the HARQ process ID (PID) used to schedule the corresponding PDSCHs.

FIG. 3 illustrates a PUCCH resource 300 showing one example of twoHARQ-ACK codebooks for multiple HARQ-ACK feedbacks multiplexed therein.When both transport block (TB) based HARQ-ACK feedback codebook 302 andcode block group (CBG) based HARQ-ACK feedback codebook 304 areconfigured, two separate HARQ-ACK codebooks may be carried by one PUCCH,such as PUCCH 300, according to some embodiments, wherein each HARQ-ACKcodebook 302 and 304 includes multiple TB based HARQ-ACK feedbacks orCBG based HARQ-ACK feedbacks. In the example, TB based HARQ-ACK feedbackand CBG based HARQ-ACK feedback are shown as being concatenated andcarried by a PUCCH.

Note that the embodiment an example of which is shown in FIG. 3 may alsobe applied for the case where SPS HARQ-ACK feedbacks are concatenatedwith TB/CBG based HARQ-ACK feedback. If the payload size of the combinedUCI exceeds the capacity of the determined PUCCH resource, certainportion of the CSI report including CSI part 1 and/or CSI part 2 may bedropped in accordance with the priority rule as defined in Section 5.2.5of T538.214 V15.2.0.

Multiplexing Multiple HARQ-ACK Feedback Reports and PUSCH

Embodiments of multiplexing multiple HARQ-ACK feedback and PUSCHs areprovided as follows below.

According to one embodiment, as shown by way of example in FIG. 4, whena plurality of PUCCH resources carrying dynamic or SPS HARQ-ACK feedbackoverlap with PUSCH, wherein PUCCHs and PUSCH are not distinguished basedon service type or priority, and if the timeline requirement as notedabove is satisfied, the UE may piggyback multiple HARQ-ACK feedbacks onPUSCH. This embodiment may also apply for the case when twonon-overlapping SPS HARQ-ACK PUCCH resources overlap with the second UCIPUCCH. The second UCI may include periodic and/or semi-persistentscheduled CSI (P/SP-CSI) report and/or SR and/or SPS HARQ-ACK feedback.

Further, in one option, multiple HARQ-ACK feedbacks may be mapped onto aPUSCH resource separately. The amount of resources for each HARQ-ACKfeedback may be calculated in accordance with the corresponding HARQ-ACKpayload size and configured/indicated beta offset. Further, the multipleHARQ-ACK feedbacks may be mapped sequentially on PUSCH based on one ormore of: the transmission timing of the first symbol HARQ-ACK feedback,the relative timing between the PDCCH monitoring occasions in which thecorresponding scheduling DC's are detected, and the relative timingbetween the first or last symbol of the scheduled PDSCHs. In oneexample, the earliest HARQ-ACK feedback in a slot is mapped first andsecond HARQ-ACK feedback is mapped after the first HARQ-ACK feedback,etc. Alternatively, the ordering of the mapping of the HARQ-ACK feedbackinformation may be determined according to the order of the HARQ processID (PID) used to schedule the corresponding PDSCHs.

In yet another option, the information bits of multiple HARQ-ACKfeedbacks may be first concatenated. The bit order of HARQ-ACK feedbackscan be defined similar to the aforementioned embodiments, as shown forexample in the context of FIG. 3. Subsequently, the concatenatedHARQ-ACK feedbacks may be modulated and mapped on PUSCH. The amount ofresource allocated for combined HARQ-ACK may calculated in accordancewith the concatenated HARQ-ACK payload size and configured/indicatedbeta offset.

FIG. 4 illustrates one example of multiplexing two HARQ-ACK feedbackswith PUSCH, including multiplexing two HARQ-ACKs and a PUSCH in a slot104 with symbols 102. In particular, FIG. 4 shows respective timefrequency resources 400 a and 400 b, where resource 400 b showsdetermined uplink resources prior to multiplexing of a first and secondHARQ-ACK feedback with a PUSCH, and resource 100 b shows uplinkresources updated after multiplexing of the first and second HARQ-ACKfeedbacks with the PUSCH according to one embodiment (updated uplinkresources). In particular, in the example, as shown in FIG. 4, two PUCCHresources 406 a and 410 a to carry separate first and second HARQ-ACKfeedbacks, respectively, are determined by the UE to overlap with aPUSCH 408 a. According to the HARQ-ACK and PUSCH multiplexing procedureof one embodiment, uplink resources may be updated by the UE in the formof PUCCH 406 b to carry the PUSCH 408 a along with the first and secondHARQ-ACK feedbacks of PUCCH resources 406 a and 410 a, respectively.Given that the determined first PUCCH resource 406 a does not overlapwith the second determined HARQ-ACK PUCCH resource 410 a in FIG. 4, theUE may therefore, according to this embodiment, transmit updated PUCCHs406 b in a slot 404 as shown in FIG. 4. This, in this embodiment, twoPUCCHs carrying separate HARQ-ACK feedbacks overlap with PUSCH.According to aforementioned examples, two HARQ-ACK feedbacks may becombined together and piggyback combined HARQ-ACK feedbacks on PUSCH.

Referring to FIG. 5, a process 500 according to one embodiment includesat operation 502, determining that UE is configured with a feature ofmultiple Physical Uplink Control Channel (PUCCH) resources with HARQ-ACKfeedback within a slot; at operation 504, determining a Physical UplinkControl Channel (PUCCH) resource to carry Hybrid Automatic RepeatRequest Acknowledgment (HARQ-ACK) feedback in response to a scheduledPhysical Downlink Shared Channel (PDSCH) resource; and at operation 506,encoding for transmission to a NR evolved NodeB (gNodeB) the PUCCHresource, the PUCCH resource to carry the HARQ-ACK feedback and: anotherPUCCH resource carrying Uplink Control Information (UCI) other thanHARQ-ACK feedback, and a scheduled Physical Uplink Shared Channel(PUSCH) resource.

FIG. 6 illustrates an architecture of a system 600 of a networkaccording to some embodiments. The system 600 is shown to include a userequipment (UE) 601 and a UE 602. The UEs 601 and 602 are illustrated assmartphones (e.g., handheld touchscreen mobile computing devicesconnectable to one or more cellular networks) but may also comprise anymobile or non-mobile computing device.

The UEs 601 and 602 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 610. The UEs 601 and 602utilize connections 603 and 604, respectively, each of which comprises aphysical communications interface or layer (discussed in further detailbelow); in this example, the connections 603 and 604 are illustrated asan air interface to enable communicative coupling and may be consistentwith cellular communications protocols.

In this embodiment, the UEs 601 and 602 may further directly exchangecommunication data via a ProSe interface 605. The ProSe interface 605may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 602 is shown to be configured to access an access point (AP) 606via connection 607. The connection 607 may comprise a local wirelessconnection, such as a connection consistent with any IEEE 802.11protocol, wherein the AP 606 would comprise a wireless fidelity (WiFi®)router. In this example, the AP 606 is shown to be connected to theInternet without connecting to the core network of the wireless system(described in further detail below).

The RAN 610 may include one or more access nodes that enable theconnections 603 and 604. These access nodes (ANs) may be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation orNew Radio evolved NodeBs (gNodeB), RAN nodes, and so forth, and maycomprise ground stations (e.g., terrestrial access points) or satellitestations providing coverage within a geographic area (e.g., a cell). TheRAN 610 may include one or more RAN nodes for providing macrocells,e.g., macro RAN node 611, and one or more RAN nodes for providingfemtocells or picocells (e.g., cells having smaller coverage areas,smaller user capacity, or higher bandwidth compared to macrocells),e.g., low power (LP) RAN node 612.

According to some embodiments, the UEs 601 and 602 may be configured tocommunicate using Orthogonal Frequency-Division Multiplexing (OFDM)communication signals with each other or with any of the RAN nodes 611and 612 over a multicarrier communication channel in accordance variouscommunication techniques, such as, but not limited to, an OrthogonalFrequency-Division Multiple Access (OFDMA) communication technique(e.g., for downlink communications) or a Single Carrier FrequencyDivision Multiple Access (SC-FDMA) communication technique (e.g., foruplink and ProSe or sidelink communications), although the scope of theembodiments is not limited in this respect. The OFDM signals maycomprise a plurality of orthogonal subcarriers.

The RAN 610 is shown to be communicatively coupled to a core network(CN) 620—via an S1 interface 613. In embodiments, the CN 620 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S1 interface 613 issplit into two parts: the S1-U interface 614, which carries traffic databetween the RAN nodes 611 and 612 and the serving gateway (S-GW) 622,and the S1-mobility management entity (MME) interface 615, which is asignalling interface between the RAN nodes 611 and 612 and MMEs 621.

The CN 620 includes network elements. The term “network element” maydescribe a physical or virtualized equipment used to provide wired orwireless communication network services. In this embodiment, the CN 620comprises, as network elements, the MMEs 621, the S-GW 622, the PacketData Network (PDN) Gateway (P-GW) 623, and a home subscriber server(HSS) 624. The MMEs 621 may be similar in function to the control planeof legacy Serving General Packet Radio Service (GPRS) Support Nodes(SGSN).

FIG. 7 illustrates example interfaces of baseband circuitry according tovarious embodiments. The baseband circuitry 700 may be included in a UEor gNodeB, for example, in UE or gNodeB of FIG. 6, and may compriseprocessors 738-742 and a memory 744 utilized by said processors. Each ofthe processors 738-732 may include a memory interface, 704A-704E,respectively, to send/receive data to/from the memory 744. Basebandcircuitry 700 may also include an audio digital signal processor (AudioDSP) 743.

The baseband circuitry 700 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 712 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 700), an application circuitryinterface 714 (e.g., an interface to send/receive data to/from anapplication circuitry), an RF circuitry interface 716 (e.g., aninterface to send/receive data to/from an RF circuitry), a wirelesshardware connectivity interface 718 (e.g., an interface to send/receivedata to/from Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components), and a power management interface 720 (e.g.,an interface to send/receive power or control signals to/from a powermanagement integrated circuit (PMIC).

The components of FIGS. 6 and/or 7, such as the shown UEs and gNodeB's,may be used in any of the embodiments described herein.

The examples set forth herein are illustrative and not exhaustive.

Example 1 includes a device of a New Radio (NR) User Equipment (UE) thedevice including a Radio Frequency (RF) interface, and processingcircuitry coupled to the RF interface, the processing circuitry to:determine an overlap between a plurality of determined Physical UplinkControl Channel (PUCCH) resources to carry respective Hybrid AutomaticRepeat Request Acknowledgment (HARQ-ACK) feedbacks and one of anotherdetermined PUCCH resource to carry an Uplink Control Information (UCI)or a determined Physical Uplink Shared Channel (PUSCH) resource to carrydata; and encode for transmission to a NR evolved NodeB (gNodeB) anupdated PUCCH resource carrying at least one of the plurality ofHARQ-ACK feedbacks and the UCI of said another determined PUCCHresource, or an updated PUSCH resource carrying the data along with theplurality of HARQ-ACK feedbacks.

Example 2 includes the subject matter of Example 1, and optionally,wherein: the plurality of determined PUCCH resources include a firstdetermined PUCCH resource and a second determined PUCCH resource; theplurality of HARQ-ACK feedbacks include a first HARQ-ACK feedback and asecond HARQ-ACK feedback corresponding to the first determined PUCCHresource and the second determined PUCCH resource, respectively; theupdated PUCCH resource is to carry the UCI of said another PUCCHresource and one of the first HARQ-ACK feedback or the second HARQ-ACKfeedback; the updated PUCCH resource, the first determined PUCCHresource and the second determined PUCCH resource are of a same serviceor priority type; and the processing circuitry is to: encode the updatedPUCCH resource and the second determined PUCCH resource for transmissionin one slot if the updated PUCCH resource is to carry the first HARQ-ACKfeedback and in response to a determination that the updated PUCCHresource does not overlap with the second determined PUCCH resource andthat one of the updated PUCCH resource or the second determined PUCCHresource is a short PUCCH resource; and encode the updated PUCCHresource and the first determined PUCCH resource for transmission in oneslot if the updated PUCCH resource is to carry the second HARQ-ACKfeedback and in response to a determination that the updated PUCCHresource does not overlap with the first determined PUCCH resource andthat one of the updated PUCCH resource or the first determined PUCCHresource is a short PUCCH resource.

Example 3 includes the subject matter of Example 1, and optionally,wherein the processing circuitry is to: decode a Downlink ControlInformation (DCI) from a NR evolved Node B (gNodeB), the DCI including aPUCCH resource indicator (PRI) field; and determine the updated PUCCHresource based the PUCCH resource indicator field in the DCI.

Example 4 includes the subject matter of Example 3, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and at least one of the plurality of HARQ-ACKfeedbacks from a corresponding at least one of the plurality ofdetermined PUCCH resources; and the processing circuitry is to: encodefor transmission in one slot the updated PUCCH resource and remainingPUCCH resources of the plurality of determined PUCCH resources carryingremaining HARQ-ACK feedbacks of the plurality of HARQ-ACK feedbacks; anddetermine the updated PUCCH resource and the remaining PUCCH resourcesbased on a combination of the PRI field and a K1 offset indicated to theUE by the gNodeB.

Example 5 includes the subject matter of Example 4, and optionally,wherein the processing circuitry is to determine the K1 by decoding oneof a Physical Downlink Shared Channel (PDSCH) resource to HARQ tinningindicator (PDSCH-to-HARQ-timing-indicator) field in the DCI or a higherlayer parameter downlink data to uplink acknowledgment (dl-DataToUL-ACK)from the gNodeB.

Example 6 includes the subject matter of Example 5, and optionally,wherein the PRI indicates a starting PUCCH symbol for each of theupdated PUCCH resource and the remaining PUCCH resources, and whereinthe processing circuitry is to determine, in units of slots, half-slotsor a set of one or more symbols, a PDSCH-end to HARQ-ACK-start timingoffset using a combination of the starting PUCCH symbol and a value ofthe PDSCH-to-HARQ-timing-indicator field.

Example 7 includes the subject matter of Example 3, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and the plurality of HARQ-ACK feedbacks; andthe processing circuitry is to determine the updated PUCCH resourcebased on the PRI field, the PRI field indicating a PUCCH resourcecarrying a first or a last dynamic HARQ-ACK feedback of the plurality ofHARQ-ACK feedbacks, wherein a resource set of the updated PUCCH resourceis based on a total payload size of the plurality of HARQ-ACK feedbacksand of the UCI of said another determined PUCCH resource.

Example 8 includes the subject matter of Example 3, and optionally,wherein the DCI is a first or last DCI scheduling a Physical DownlinkShared Channel (PDSCH) for which the plurality of HARQ-ACK feedbacks areto be scheduled, and wherein the plurality of HARQ-ACK feedbacks in theupdated PUCCH resource are to be scheduled in a slot.

Example 9 includes the subject matter of Example 1, and optionally,wherein a bit order in a same slot of said at least one of the pluralityof HARQ-ACK feedbacks is to follow a timing of the said at least one ofthe plurality of HARQ-ACK feedbacks.

Example 10 includes the subject matter of Example 1, and optionally,wherein an ordering of a mapping of information for said at least one ofthe plurality of HARQ-ACK feedbacks is based on an order of HARQ processidentifications (PIDs) used to schedule corresponding Physical DownlinkShared Channel (PDSCH) resources.

Example 11 includes the subject matter of Example 1, and optionally,wherein the at least one of the plurality of HARQ-ACK feedbacks includestransport block (TB) based HARQ-ACK feedbacks and code block group (CBG)based HARQ-ACK feedbacks, the updated PUCCH resource to carry twoseparate HARQ-ACK codebooks corresponding to the TB based HARQ-ACKfeedbacks and to the CBG based HARQ-ACK feedbacks respectively.

Example 12 includes the subject matter of Example 1, and optionally,wherein: the plurality of HARQ-ACK feedbacks include dynamic HARQ-ACKfeedbacks and semi-persistent scheduling HARQ-ACK feedbacks; and theprocessing circuitry is to encode the updated PUSCH resource to carrythe UCI of said another PUCCH resource and the HARQ-ACK feedbacks inresponse to a determination that the updated PUSCH resource and theplurality of determined PUCCH resources are of a same service orpriority type.

Example 13 includes the subject matter of Example 12, and optionally,wherein the processing circuitry is to encode the updated PUSH bymapping the plurality of HARQ-ACK feedbacks into the updated PUSCHseparately and by allocating an amount of resources for each HARQ-ACKfeedback based on a payload size and a beta offset of each respectiveone of the plurality of HARQ-ACK feedbacks.

Example 14 includes the subject matter of Example 12, and optionally,wherein the processing circuitry is to concatenate information bits ofthe plurality of HARQ-ACK feedbacks to multiplex the HARQ-ACK feedbacksinto the updated PUSCH.

Example 15 includes the device of any one of Examples 1-14, furtherincluding a front end module coupled to the RF interface.

Example 16 includes the subject matter of Example 15, and optionally,further including one or more antennas coupled to the front end moduleto transmit the updated PUCCH resource or updated PUSCH resource.

Example 17 includes a method to be performed at a device of a New Radio(NR) User Equipment (UE), the method including: determining an overlapbetween a plurality of determined Physical Uplink Control Channel(PUCCH) resources to carry respective Hybrid Automatic Repeat RequestAcknowledgment (HARQ-ACK) feedbacks and one of another determined PUCCHresource to carry an Uplink Control Information (UCI) or a determinedPhysical Uplink Shared Channel (PUSCH) resource to carry data; andencoding for transmission to a NR evolved NodeB (gNodeB) an updatedPUCCH resource carrying at least one of the plurality of HARQ-ACKfeedbacks and the UCI of said another determined PUCCH resource, or anupdated PUSCH resource carrying the data along with the plurality ofHARQ-ACK feedbacks.

Example 18 includes the subject matter of Example 17, and optionally,wherein: the plurality of determined PUCCH resources include a firstdetermined PUCCH resource and a second determined PUCCH resource; theplurality of HARQ-ACK feedbacks include a first HARQ-ACK feedback and asecond HARQ-ACK feedback corresponding to the first determined PUCCHresource and the second determined PUCCH resource, respectively; theupdated PUCCH resource is to carry the UCI of said another PUCCHresource and one of the first HARQ-ACK feedback or the second HARQ-ACKfeedback; the updated PUCCH resource, the first determined PUCCHresource and the second determined PUCCH resource are of a same serviceor priority type; and the method further includes: encoding the updatedPUCCH resource and the second determined PUCCH resource for transmissionin one slot if the updated PUCCH resource is to carry the first HARQ-ACKfeedback and in response to a determination that the updated PUCCHresource does not overlap with the second determined PUCCH resource andthat one of the updated PUCCH resource or the second determined PUCCHresource is a short PUCCH resource; and encoding the updated PUCCHresource and the first determined PUCCH resource for transmission in oneslot if the updated PUCCH resource is to carry the second HARQ-ACKfeedback and in response to a determination that the updated PUCCHresource does not overlap with the first determined PUCCH resource andthat one of the updated PUCCH resource or the first determined PUCCHresource is a short PUCCH resource.

Example 19 includes the subject matter of Example 17, and optionally,the method further including: decoding a Downlink Control Information(DCI) from a NR evolved Node B (gNodeB), the DCI including a PUCCHresource indicator (PRI) field; and determining the updated PUCCHresource based the PUCCH resource indicator field in the DCI.

Example 20 includes the subject matter of Example 19, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and at least one of the plurality of HARQ-ACKfeedbacks from a corresponding at least one of the plurality ofdetermined PUCCH resources; and the method further includes: encodingfor transmission in one slot the updated PUCCH resource and remainingPUCCH resources of the plurality of determined PUCCH resources carryingremaining HARQ-ACK feedbacks of the plurality of HARQ-ACK feedbacks; anddetermining the updated PUCCH resource and the remaining PUCCH resourcesbased on a combination of the PRI field and a K1 offset indicated to theUE by the gNodeB.

Example 21 includes the subject matter of Example 20, and optionally,further including determining the K1 offset by decoding one of aPhysical Downlink Shared Channel (PDSCH) resource to HARQ timingindicator (PDSCH-to-HARQ-timing-indicator) field in the DCI or a higherlayer parameter downlink data to uplink acknowledgment (dl-DataToUL-ACK)from the gNodeB.

Example 22 includes the subject matter of Example 21, and optionally,wherein the PRI indicates a starting PUCCH symbol for each of theupdated PUCCH resource and the remaining PUCCH resources, and whereinthe method further includes determining, in units of slots, half-slotsor a set of one or more symbols, a PDSCH-end to HARQ-ACK-start timingoffset using a combination of the starting PUCCH symbol and a value ofthe PDSCH-to-HARQ-timing-indicator field.

Example 23 includes the subject matter of Example 19, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and the plurality of HARQ-ACK feedbacks; andthe method further includes determining the updated PUCCH resource basedon the PRI field, the PRI field indicating a PUCCH resource carrying afirst or a last dynamic HARQ-ACK feedback of the plurality of HARQ-ACKfeedbacks, wherein a resource set of the updated PUCCH resource is basedon a total payload size of the plurality of HARQ-ACK feedbacks and ofthe UCI of said another determined PUCCH resource.

Example 24 includes the subject matter of Example 19, and optionally,wherein the DCI is a first or last DCI scheduling a Physical DownlinkShared Channel (PDSCH) for which the plurality of HARQ-ACK feedbacks areto be scheduled, and wherein the plurality of HARQ-ACK feedbacks in theupdated PUCCH resource are to be scheduled in a slot.

Example 25 includes the subject matter of Example 17, and optionally,wherein a bit order in a same slot of said at least one of the pluralityof HARQ-ACK feedbacks is to follow a timing of the said at least one ofthe plurality of HARQ-ACK feedbacks.

Example 26 includes the subject matter of Example 17, and optionally,wherein an ordering of a mapping of information for said at least one ofthe plurality of HARQ-ACK feedbacks is based on an order of HARQ processidentifications (PIDs) used to schedule corresponding Physical DownlinkShared Channel (PDSCH) resources.

Example 27 includes the subject matter of Example 17, and optionally,wherein the at least one of the plurality of HARQ-ACK feedbacks includestransport block (TB) based HARQ-ACK feedbacks and code block group (CBG)based HARQ-ACK feedbacks, the updated PUCCH resource to carry twoseparate HARQ-ACK codebooks corresponding to the TB based HARQ-ACKfeedbacks and to the CBG based HARQ-ACK feedbacks respectively.

Example 28 includes the subject matter of Example 17, and optionally,wherein: the plurality of HARQ-ACK feedbacks include dynamic HARQ-ACKfeedbacks and semi-persistent scheduling HARQ-ACK feedbacks; and themethod further includes encoding the updated PUSCH resource to carry theUCI of said another PUCCH resource and the HARQ-ACK feedbacks inresponse to a determination that the updated PUSCH resource and theplurality of determined PUCCH resources are of a same service orpriority type.

Example 29 includes the subject matter of Example 28, and optionally,further including encoding the updated PUSH by mapping the plurality ofHARQ-ACK feedbacks into the updated PUSCH separately and by allocatingan amount of resources for each HARQ-ACK feedback based on a payloadsize and a beta offset of each respective one of the plurality ofHARQ-ACK feedbacks.

Example 30 includes the subject matter of Example 28, and optionally,further including concatenating information bits of the plurality ofHARQ-ACK feedbacks to multiplex the HARQ-ACK feedbacks into the updatedPUSCH.

Example 31 includes a device of a New Radio (NR) User Equipment (UE),the device including: means for determining an overlap between aplurality of determined Physical Uplink Control Channel (PUCCH)resources to carry respective Hybrid Automatic Repeat RequestAcknowledgment (HARQ-ACK) feedbacks and one of another determined PUCCHresource to carry an Uplink Control Information (UCI) or a determinedPhysical Uplink Shared Channel (PUSCH) resource to carry data; and meansfor encoding for transmission to a NR evolved NodeB (gNodeB) an updatedPUCCH resource carrying at least one of the plurality of HARQ-ACKfeedbacks and the UCI of said another determined PUCCH resource, or anupdated PUSCH resource carrying the data along with the plurality ofHARQ-ACK feedbacks.

Example 32 includes the subject matter of Example 31, and optionally,wherein: the plurality of determined PUCCH resources include a firstdetermined PUCCH resource and a second determined PUCCH resource; theplurality of HARQ-ACK feedbacks include a first HARQ-ACK feedback and asecond HARQ-ACK feedback corresponding to the first determined PUCCHresource and the second determined PUCCH resource, respectively; theupdated PUCCH resource is to carry the UCI of said another PUCCHresource and one of the first HARQ-ACK feedback or the second HARQ-ACKfeedback; the updated PUCCH resource, the first determined PUCCHresource and the second determined PUCCH resource are of a same serviceor priority type; and the device further includes: means for encodingthe updated PUCCH resource and the second determined PUCCH resource fortransmission in one slot if the updated PUCCH resource is to carry thefirst HARQ-ACK feedback and in response to a determination that theupdated PUCCH resource does not overlap with the second determined PUCCHresource and that one of the updated PUCCH resource or the seconddetermined PUCCH resource is a short PUCCH resource; and means forencoding the updated PUCCH resource and the first determined PUCCHresource for transmission in one slot if the updated PUCCH resource isto carry the second HARQ-ACK feedback and in response to a determinationthat the updated PUCCH resource does not overlap with the firstdetermined PUCCH resource and that one of the updated PUCCH resource orthe first determined PUCCH resource is a short PUCCH resource.

Example 33 includes a device of a New Radio (NR) evolved NodeB (gNodeB),the device including a Radio Frequency (RF) interface, and processingcircuitry coupled to the RF interface, the processing circuitry to:encode a Downlink Control Information (DCI) for transmission to a NRUser Equipment (UE), the DCI including a PUCCH resource indicator (PRI)field to allow a UE to determine an updated Physical Uplink ControlChannel (PUCCH) resource from the PRI, wherein the updated PUCCHresource is to carry at least one HARQ-ACK feedback of a plurality ofHARQ-ACK feedbacks corresponding to a plurality of determined PUCCHresources of the UE respectively, and an Uplink Control Information(UCI) of another determined PUCCH resource of the UE; and decode theupdated PUCCH from the UE.

Example 34 includes the subject matter of Example 33, and optionally,wherein: the updated PUCCH resource is to carry the at least oneHARQ-ACK feedback, and remaining PUCCH resources of the plurality ofdetermined PUCCH resources carrying respective remaining HARQ-ACKfeedbacks of the plurality of HARQ-ACK feedbacks; and the processingcircuitry is to encode for transmission to the UE a K1 offset, acombination of the PRI field and a K1 offset to allow the UE todetermine the updated PUCCH resource and the remaining PUCCH resources.

Example 35 includes the subject matter of Example 34, and optionally,wherein the K1 offset is based on one of a Physical Downlink SharedChannel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI or a higher layerparameter downlink data to uplink acknowledgment (dl-DataToUL-ACK) fromthe gNodeB to the UE.

Example 36 includes the subject matter of Example 35, and optionally,wherein the PRI indicates a starting PUCCH symbol for each of theupdated PUCCH resource and the remaining PUCCH resources, and wherein, acombination of the starting PUCCH symbol and a value of thePDSCH-to-HARQ-timing-indicator field is to allow the UE to determine aPDSCH-end to HARQ-ACK-start timing offset in units of slots, half-slotsor a set of one or more symbols.

Example 37 includes the subject matter of Example 33, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and the plurality of HARQ-ACK feedbacks; andthe PRI field indicates a PUCCH resource carrying a first or a lastdynamic HARQ-ACK feedback of the plurality of HARQ-ACK feedbacks,wherein a resource set of the updated PUCCH resource is based on a totalpayload size of the plurality of HARQ-ACK feedbacks and of the UCI ofsaid another determined PUCCH resource.

Example 38 includes the subject matter of Example 33, and optionally,wherein the DCI is a first or last DCI scheduling a Physical DownlinkShared Channel (PDSCH) for which the plurality of HARQ-ACK feedbacks areto be scheduled, and wherein the plurality of HARQ-ACK feedbacks in theupdated PUCCH resource are to be scheduled in a slot.

Example 39 includes the subject matter of Example 33, and optionally,wherein a bit order in a same slot of said at least one of the pluralityof HARQ-ACK feedbacks is to follow a timing of the said at least one ofthe plurality of HARQ-ACK feedbacks.

Example 40 includes the subject matter of Example 33, and optionally,wherein an ordering of a mapping of information for said at least one ofthe plurality of HARQ-ACK feedbacks is based on an order of HARQ processidentifications (PIDs) used to schedule corresponding Physical DownlinkShared Channel (PDSCH) resources.

Example 41 includes the subject matter of Example 33, and optionally,wherein the at least one of the plurality of HARQ-ACK feedbacks includestransport block (TB) based HARQ-ACK feedbacks and code block group (CBG)based HARQ-ACK feedbacks, the updated PUCCH resource to carry twoseparate HARQ-ACK codebooks corresponding to the TB based HARQ-ACKfeedbacks and to the CBG based HARQ-ACK feedbacks respectively.

Example 42 includes the subject matter of any one of Examples 33-41, andoptionally, further including a front end module coupled to the RFinterface.

Example 43 includes the subject matter of Example 42, and optionally,further including one or more antennas coupled to the front end moduleto transmit the DCI and to receive the updated PUCCH.

Example 44 includes a method to be used at a device of a New Radio (NR)evolved NodeB (gNodeB), the method including: encoding a DownlinkControl Information (DCI) for transmission to a NR User Equipment (UE),the DCI including a PUCCH resource indicator (PRI) field to allow a UEto determine an updated Physical Uplink Control Channel (PUCCH) resourcefrom the PRI, wherein the updated PUCCH resource is to carry at leastone HARQ-ACK feedback of a plurality of HARQ-ACK feedbacks correspondingto a plurality of determined PUCCH resources of the UE respectively, andan Uplink Control Information (UCI) of another determined PUCCH resourceof the UE; and decoding the updated PUCCH from the UE.

Example 45 includes the subject matter of Example 44, and optionally,wherein: the updated PUCCH resource is to carry the at least oneHARQ-ACK feedback, and remaining PUCCH resources of the plurality ofdetermined PUCCH resources carrying respective remaining HARQ-ACKfeedbacks of the plurality of HARQ-ACK feedbacks; and the methodincludes encoding for transmission to the UE a K1 offset, a combinationof the PRI field and a K1 offset to allow the UE to determine theupdated PUCCH resource and the remaining PUCCH resources.

Example 46 includes the subject matter of Example 45, and optionally,wherein the K1 offset is based on one of a Physical Downlink SharedChannel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI or a higher layerparameter downlink data to uplink acknowledgment (dl-DataToUL-ACK) fromthe gNodeB to the UE.

Example 47 includes the subject matter of Example 46, and optionally,wherein the PRI indicates a starting PUCCH symbol for each of theupdated PUCCH resource and the remaining PUCCH resources, and wherein, acombination of the starting PUCCH symbol and a value of thePDSCH-to-HARQ-timing-indicator field is to allow the UE to determine aPDSCH-end to HARQ-ACK-start timing offset in units of slots, half-slotsor a set of one or more symbols.

Example 48 includes the subject matter of Example 44, and optionally,wherein: the updated PUCCH resource is to carry the UCI of said anotherdetermined PUCCH resource and the plurality of HARQ-ACK feedbacks; andthe PRI field indicates a PUCCH resource carrying a first or a lastdynamic HARQ-ACK feedback of the plurality of HARQ-ACK feedbacks,wherein a resource set of the updated PUCCH resource is based on a totalpayload size of the plurality of HARQ-ACK feedbacks and of the UCI ofsaid another determined PUCCH resource.

Example 49 includes the subject matter of Example 44, and optionally,wherein the DCI is a first or last DCI scheduling a Physical DownlinkShared Channel (PDSCH) for which the plurality of HARQ-ACK feedbacks areto be scheduled, and wherein the plurality of HARQ-ACK feedbacks in theupdated PUCCH resource are to be scheduled in a slot.

Example 50 includes the subject matter of Example 44, and optionally,wherein a bit order in a same slot of said at least one of the pluralityof HARQ-ACK feedbacks is to follow a timing of the said at least one ofthe plurality of HARQ-ACK feedbacks.

Example 51 includes the subject matter of Example 44, and optionally,wherein an ordering of a mapping of information for said at least one ofthe plurality of HARQ-ACK feedbacks is based on an order of HARQ processidentifications (PIDs) used to schedule corresponding Physical DownlinkShared Channel (PDSCH) resources.

Example 52 includes the subject matter of Example 44, and optionally,wherein the at least one of the plurality of HARQ-ACK feedbacks includestransport block (TB) based HARQ-ACK feedbacks and code block group (CBG)based HARQ-ACK feedbacks, the updated PUCCH resource to carry twoseparate HARQ-ACK codebooks corresponding to the TB based HARQ-ACKfeedbacks and to the CBG based HARQ-ACK feedbacks respectively.

Example 53 includes a device of a New Radio (NR) evolved NodeB (gNodeB)including: means for encoding a Downlink Control Information (DCI) fortransmission to a NR User Equipment (UE), the DCI including a PUCCHresource indicator (PRI) field to allow a UE to determine an updatedPhysical Uplink Control Channel (PUCCH) resource from the PRI, whereinthe updated PUCCH resource is to carry at least one HARQ-ACK feedback ofa plurality of HARQ-ACK feedbacks corresponding to a plurality ofdetermined PUCCH resources of the UE respectively, and an Uplink ControlInformation (UCI) of another determined PUCCH resource of the UE; andmeans for decoding the updated PUCCH from the UE.

Example 54 includes the subject matter of Example 53, and optionally,wherein: the updated PUCCH resource is to carry the at least oneHARQ-ACK feedback, and remaining PUCCH resources of the plurality ofdetermined PUCCH resources carrying respective remaining HARQ-ACKfeedbacks of the plurality of HARQ-ACK feedbacks; and the deviceincludes means for encoding for transmission to the UE a K1 offset, acombination of the PRI field and a K1 offset to allow the UE todetermine the updated PUCCH resource and the remaining PUCCH resources.

Example 55 includes a device of a New Radio (NR) User Equipment (UE) thedevice including a Radio Frequency (RF) interface, and processingcircuitry coupled to the RF interface, the processing circuitry to:determine that the UE is configured with a feature of multiple PhysicalUplink Control Channel (PUCCH) resources with HARQ-ACK feedback within aslot; determine a Physical Uplink Control Channel (PUCCH) resource tocarry Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedbackin response to a scheduled Physical Downlink Shared Channel (PDSCH)resource; and encode for transmission to a NR evolved NodeB (gNodeB) thePUCCH resource, the PUCCH resource to carry the HARQ-ACK feedback and:another PUCCH resource carrying Uplink Control Information (UCI) otherthan HARQ-ACK feedback, and a scheduled Physical Uplink Shared Channel(PUSCH) resource.

Example 56 includes the subject matter of Example 55, and optionally,wherein the processing circuitry is to: decode a Downlink ControlInformation (DCI) from the gNodeB including a PUCCH resource indicator(PRI) field; and determine the PUCCH resource based on the PRI and a K1offset value, wherein the K1 offset value is based on a PhysicalDownlink Shared Channel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI format or on a higherlayer parameter downlink data to uplink acknowledgment (dl-DataToUL-ACK)from the gNodeB.

Example 57 includes the subject matter of Example 56, and optionally,wherein the DCI format corresponds to a DCI format scheduling thescheduled PDSCH resource, the processing circuitry to determine thePUCCH resource for HARQ-ACK feedback based on a starting symbol of thePUCCH resource.

Example 58 includes the subject matter of Example 57, and optionally,wherein the DCI format corresponds to a DCI format scheduling thescheduled PDSCH, the processing circuitry to determine the PUCCHresource for HARQ-ACK feedback based on a reference point thatcorresponds to one of: a beginning of a slot, a beginning of ahalf-slot, a beginning of a sub-slot, wherein a sub-slot corresponds toa set of consecutive OFDM symbols and is based on a configuration of atiming relationship between different sets of transmission opportunitiesfor the PUCCH with HARQ-ACK feedback.

Example 59 includes the subject matter of Example 56, and optionally,wherein the K1 offset value indicates a time between an end of thescheduled PDSCH and an earliest start of the PUCCH carrying the HARQ-ACKfeedback, in units of slots, half-slots, or sub-slots, wherein asub-slot corresponds to a set of consecutive OFDM symbols and is basedon a configuration of a timing relationship between different sets oftransmission opportunities for the PUCCH with HARQ-ACK feedback.

Example 60 includes the subject matter of Example 55, and optionally,wherein the processing circuitry is configured to: determine saidanother PUCCH resource carrying UCI other than HARQ-ACK feedback, andsaid scheduled PUSCH resource; determine whether at least one of saidanother PUCCH resource and said scheduled PUSCH resource overlap in timewith a determined PUCCH resource to carry HARQ-ACK feedback; anddetermine, for transmission to the gNodeB, one of: an updated PUCCHresource carrying at least one bit of HARQ-ACK feedback and the UCIother than HARQ-ACK feedback, or an updated PUSCH resource to carry atleast one bit of HARQ-ACK feedback multiplexed with Uplink SharedChannel (USCH) and a UCI other than the UCI.

Example 61 includes the subject matter of Example 60, and optionally,wherein: the updated PUCCH resource is to carry a combined UCI includinginformation bits corresponding to respective ones of the HARQ-ACKfeedbacks; and the processing circuitry is to: decode a Downlink ControlInformation (DCI) from the gNodeB including a PUCCH resource indicator(PRI) field; determine the updated PUCCH resource based on the PRIfield, the PRI field indicating a PUCCH resource carrying a first or alast dynamic HARQ-ACK feedback of the one or more bits of HARQ-ACKfeedback; determine a PUCCH resource set based on a total payload sizeof the combined UCI; and select a PUCCH resource from the PUCCH resourceset using the PRI.

Example 62 includes the subject matter of Example 60, and optionally,wherein, in response to a determination that a plurality of PUCCHresources carrying dynamic or semi-persistent scheduled (SPS) HARQ-ACKfeedbacks overlap with the scheduled PUSCH resource, and that theplurality of PUCC resources and the scheduled PUSCH resource are from asame service type or priority, the processing circuitry is to encodeinformation bits corresponding to respective ones of the HARQ-ACKfeedbacks onto the updated PUSCH resource.

Example 63 includes the subject matter of Example 62, and optionally,wherein the processing circuitry is to encode and map information bitscorresponding to respective ones of the HARQ-ACK feedbacks into theupdated PUSCH resource separately, and to allocate an amount ofresources for each of the information bits corresponding to respectiveones of the HARQ-ACK feedbacks based on a payload size and a beta offsetof each of the information bits corresponding to respective ones of theHARQ-ACK feedbacks.

Example 64 includes the subject matter of Example 62, and optionally,wherein the processing circuitry is to concatenate the information bitscorresponding to respective ones of the HARQ-ACK feedbacks to multiplexinformation bits corresponding to respective ones of the HARQ-ACKfeedbacks into the updated PUSCH resource.

Example 65 includes the subject matter of any one of Examples 55-63, andoptionally, wherein further including a front end module coupled to theRF interface.

Example 66 includes the subject matter of Example 65, and optionally,further including one or more antennas coupled to the front end moduleto transmit the updated PUCCH resource or updated PUSCH resource.

Example 67 includes a method to be performed at a device of a New Radio(NR) User Equipment (UE) the method including: determining that the UEis configured with a feature of multiple Physical Uplink Control Channel(PUCCH) resources with HARQ-ACK feedback within a slot; determining aPhysical Uplink Control Channel (PUCCH) resource to carry HybridAutomatic Repeat Request Acknowledgment (HARQ-ACK) feedback in responseto a scheduled Physical Downlink Shared Channel (PDSCH) resource; andencoding for transmission to a NR evolved NodeB (gNodeB) the PUCCHresource, the PUCCH resource to carry the HARQ-ACK feedback and: anotherPUCCH resource carrying Uplink Control Information (UCI) other thanHARQ-ACK feedback, and a scheduled Physical Uplink Shared Channel(PUSCH) resource.

Example 68 includes the subject matter of Example 67, and optionally,the method further including: decoding a Downlink Control Information(DCI) from the gNodeB including a PUCCH resource indicator (PRI) field;and determining the PUCCH resource based on the PRI and a K1 offsetvalue, wherein the K1 offset value is based on a Physical DownlinkShared Channel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI format or on a higherlayer parameter downlink data to uplink acknowledgment (dl-DataToUL-ACK)from the gNodeB.

Example 69 includes the subject matter of Example 68, and optionally,wherein the DCI format corresponds to a DCI format scheduling thescheduled PDSCH resource, the method including determining the PUCCHresource for HARQ-ACK feedback based on a starting symbol of the PUCCHresource.

Example 70 includes the subject matter of Example 69 wand optionally,herein the DCI format corresponds to a DCI format scheduling thescheduled PDSCH, the method including determining the PUCCH resource forHARQ-ACK feedback based on a reference point that corresponds to one of:a beginning of a slot, a beginning of a half-slot, a beginning of asub-slot, wherein a sub-slot corresponds to a set of consecutive OFDMsymbols and is based on a configuration of a timing relationship betweendifferent sets of transmission opportunities for the PUCCH with HARQ-ACKfeedback.

Example 71 includes the subject matter of Example 68, and optionally,wherein the K1 offset value indicates a time between an end of thescheduled PDSCH and an earliest start of the PUCCH carrying the HARQ-ACKfeedback, in units of slots, half-slots, or sub-slots, wherein asub-slot corresponds to a set of consecutive OFDM symbols and is basedon a configuration of a timing relationship between different sets oftransmission opportunities for the PUCCH with HARQ-ACK feedback.

Example 72 includes the subject matter of Example 67, and optionally,the method further including: determining said another PUCCH resourcecarrying UCI other than HARQ-ACK feedback, and said scheduled PUSCHresource; determining whether at least one of said another PUCCHresource and said scheduled PUSCH resource overlap in time with adetermined PUCCH resource to carry HARQ-ACK feedback; and determining,for transmission to the gNodeB, one of: an updated PUCCH resourcecarrying at least one bit of HARQ-ACK feedback and the UCI other thanHARQ-ACK feedback, or an updated PUSCH resource to carry at least onebit of HARQ-ACK feedback multiplexed with Uplink Shared Channel (USCH)and a UCI other than the UCI.

Example 73 includes the subject matter of Example 72, and optionally,wherein: the updated PUCCH resource is to carry a combined UCI includinginformation bits corresponding to respective ones of the HARQ-ACKfeedbacks; and the method further includes: decoding a Downlink ControlInformation (DCI) from the gNodeB including a PUCCH resource indicator(PRI) field; determining the updated PUCCH resource based on the PRIfield, the PRI field indicating a PUCCH resource carrying a first or alast dynamic HARQ-ACK feedback of the one or more bits of HARQ-ACKfeedback; determining a PUCCH resource set based on a total payload sizeof the combined UCI; and selecting a PUCCH resource from the PUCCHresource set using the PRI.

Example 74 includes the subject matter of Example 72, and optionally,wherein the method further includes, in response to a determination thata plurality of PUCCH resources carrying dynamic or semi-persistentscheduled (SPS) HARQ-ACK feedbacks overlap with the scheduled PUSCHresource, and that the plurality of PUCC resources and the scheduledPUSCH resource are from a same service type or priority, encodinginformation bits corresponding to respective ones of the HARQ-ACKfeedbacks onto the updated PUSCH resource.

Example 75 includes the subject matter of Example 74, and optionally,the method further including encoding and mapping information bitscorresponding to respective ones of the HARQ-ACK feedbacks into theupdated PUSCH resource separately, and to allocate an amount ofresources for each of the information bits corresponding to respectiveones of the HARQ-ACK feedbacks based on a payload size and a beta offsetof each of the information bits corresponding to respective ones of theHARQ-ACK feedbacks.

Example 76 includes the subject matter of Example 74, and optionally,the method further including concatenating the information bitscorresponding to respective ones of the HARQ-ACK feedbacks to multiplexinformation bits corresponding to respective ones of the HARQ-ACKfeedbacks into the updated PUSCH resource.

Example 77 includes a device of a New Radio (NR) User Equipment (UE) thedevice including: means for determining that the UE is configured with afeature of multiple Physical Uplink Control Channel (PUCCH) resourceswith HARQ-ACK feedback within a slot; means for determining a PhysicalUplink Control Channel (PUCCH) resource to carry Hybrid Automatic RepeatRequest Acknowledgment (HARQ-ACK) feedback in response to a scheduledPhysical Downlink Shared Channel (PDSCH) resource; and encoding fortransmission to a NR evolved NodeB (gNodeB) the PUCCH resource, thePUCCH resource to carry the HARQ-ACK feedback and: another PUCCHresource carrying Uplink Control Information (UCI) other than HARQ-ACKfeedback, and a scheduled Physical Uplink Shared Channel (PUSCH)resource.

Example 78 includes the subject matter of Example 77, and optionally,further including: means for decoding a Downlink Control Information(DCI) from the gNodeB including a PUCCH resource indicator (PRI) field;and means for determining the PUCCH resource based on the PRI and a K1offset value, wherein the K1 offset value is based on a PhysicalDownlink Shared Channel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI format or on a higherlayer parameter downlink data to uplink acknowledgment (dl-DataToUL-ACK)from the gNodeB.

Example 79 includes a machine-readable medium including code which, whenexecuted, is to cause a machine to perform the method of any one of theExamples above.

Example 80 includes a machine-readable medium including code which, whenexecuted, is to cause a machine to perform the method of any one of theExamples above.

Example 81 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one processor to perform themethod of any one of the Examples above.

Example 82 includes a method to be performed at a device of a New Radio(NR) evolved Node B, the method including performing the functionalitiesof a baseband processing circuitry associated with a gNodeB as set forthin any of the Examples above.

Example 83 includes a device of a of a New Radio (NR) evolved Node B,the device including a Radio Frequency (RF) interface and a processingcircuitry coupled to the RF interface, the processing circuitry toperform the functionalities of a baseband processing circuitryassociated with a gNodeB as set forth in any of the Examples above.

Example 84 includes an apparatus comprising means for causing a wirelesscommunication device to perform the method of any one of the aboveExamples.

Example 85 includes a machine-readable medium including code which, whenexecuted, is to cause a machine to perform the method of any one of theabove Examples.

Example 86 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toperform the method of any one of the above Examples.

Example 87 includes an apparatus comprising means for causing a wirelesscommunication device to perform the method of any one of the aboveExamples.

Example 88 may include a signal as described in or related to any of theexamples above, or portions or parts thereof.

Example 89 may include a signal in a wireless network as shown anddescribed herein.

Example 90 may include a method of communicating in a wireless networkas shown and described herein.

Example 91 may include a system for providing wireless communication asshown and described herein.

Any of the above-described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed.

1. A User Equipment (UE) the device including a Radio Frequency (RF)interface, and processing circuitry coupled to the RF interface, theprocessing circuitry to: determine that the UE is configured with afeature of multiple Physical Uplink Control Channel (PUCCH) resourceswith Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback withina slot; determine a Physical Uplink Control Channel (PUCCH) resource tocarry Hybrid HARQ-ACK feedback in response to a scheduled PhysicalDownlink Shared Channel (PDSCH) resource; and encode for transmission toa base station (BS) the PUCCH resource, the PUCCH resource to carry theHARQ-ACK feedback, and another PUCCH resource carrying Uplink ControlInformation (UCI) other than HARQ-ACK feedback, and a scheduled PhysicalUplink Shared Channel (PUSCH) resource.
 2. The UE of claim 1, whereinthe processing circuitry is to: decode a Downlink Control Information(DCI) from the BS including a PUCCH resource indicator (PRI) field; anddetermine the PUCCH resource based on the PRI and a K1 offset value,wherein the K1 offset value is based on a Physical Downlink SharedChannel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI or on a higher layerparameter downlink data to uplink acknowledgment (dl-DataToUL-ACK) fromthe BS.
 3. The UE of claim 2, wherein the DCI corresponds to a DCIscheduling the scheduled PDSCH resource, the processing circuitry todetermine the PUCCH resource for HARQ-ACK feedback based on a startingsymbol of the PUCCH resource.
 4. The UE of claim 2, wherein the DCIcorresponds to a DCI scheduling the scheduled PDSCH resource, theprocessing circuitry to determine the PUCCH resource for HARQ-ACKfeedback based on a reference point that corresponds to one of: abeginning of a slot, a beginning of a half-slot, g a beginning of asub-slot, wherein the sub-slot corresponds to a set of consecutive OFDMsymbols and is based on a configuration of a timing relationship betweendifferent sets of transmission opportunities for the PUCCH resource withHARQ-ACK feedback.
 5. The UE of claim 2, wherein the K1 offset valueindicates a time between an end of the scheduled PDSCH resource and anearliest start of the PUCCH resource carrying the HARQ-ACK feedback, inunits of slots, half-slots, or sub-slots, wherein a sub-slot correspondsto a set of consecutive OFDM symbols and is based on a configuration ofa timing relationship between different sets of transmissionopportunities for the PUCCH resource with HARQ-ACK feedback.
 6. The UEof claim 1, wherein the processing circuitry is configured to: determineanother PUCCH resource carrying UCI other than HARQ-ACK feedback, andthe scheduled PUSCH resource; determine whether at least one of theanother PUCCH resource and the scheduled PUSCH resource overlap in timewith a determined PUCCH resource to carry HARQ-ACK feedback; anddetermine, for transmission to the BS, one of: an updated PUCCH resourcecarrying at least one bit of HARQ-ACK feedback and the UCI other thanHARQ-ACK feedback, or an updated PUSCH resource to carry at least onebit of HARQ-ACK feedback multiplexed with Uplink Shared Channel (USCH)and another UCI other than the UCI.
 7. The UE of claim 6, wherein: theupdated PUCCH resource is to carry a combined UCI including informationbits corresponding to respective ones of the HARQ-ACK feedbacks; and theprocessing circuitry is to: decode a Downlink Control Information (DCI)from the BS including a PUCCH resource indicator (PRI) field; determinethe updated PUCCH resource based on the PRI field, the PRI fieldindicating a PUCCH resource carrying a first or a last dynamic HARQ-ACKfeedback of the one or more bits of HARQ-ACK feedback; determine a PUCCHresource set based on a total payload size of the combined UCI; andselect a PUCCH resource from the PUCCH resource set using the PRI. 8.The UE of claim 6, wherein, in response to a determination that aplurality of PUCCH resources carrying dynamic or semi-persistentscheduled (SPS) HARQ-ACK feedbacks overlap with the scheduled PUSCHresource, and that the plurality of PUCCH resources and the scheduledPUSCH resource are from a same service type or priority, the processingcircuitry is to encode information bits corresponding to respective onesof the HARQ-ACK feedbacks onto the updated PUSCH resource. 9-12.(canceled)
 13. A method to be performed at a User Equipment (UE) themethod including: determining that the UE is configured with a featureof multiple Physical Uplink Control Channel (PUCCH) resources withHybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedbackwithin a slot; determining a Physical Uplink Control Channel (PUCCH)resource to carry HARQ-ACK feedback in response to a scheduled PhysicalDownlink Shared Channel (PDSCH) resource; and encoding for transmissionto a base station (BS) the PUCCH resource, the PUCCH resource to carrythe HARQ-ACK feedback and: another PUCCH resource carrying UplinkControl Information (UCI) other than HARQ-ACK feedback, and a scheduledPhysical Uplink Shared Channel (PUSCH) resource.
 14. The method of claim13, the method further including: decoding a Downlink ControlInformation (DCI) from the BS including a PUCCH resource indicator (PRI)field; and determining the PUCCH resource based on the PRI and a K1offset value, wherein the K1 offset value is based on a PhysicalDownlink Shared Channel (PDSCH) resource to HARQ timing indicator(PDSCH-to-HARQ-timing-indicator) field in the DCI or on a higher layerparameter downlink data to uplink acknowledgment (dl-DataToUL-ACK) fromthe BS.
 15. The method of claim 14, wherein the DCI corresponds to a DCIscheduling the scheduled PDSCH resource, the method includingdetermining the PUCCH resource for HARQ-ACK feedback based on a startingsymbol of the PUCCH resource.
 16. The method of claim 14, wherein theDCI corresponds to a DCI scheduling the scheduled PDSCH, the methodincluding determining the PUCCH resource for HARQ-ACK feedback based ona reference point that corresponds to one of: a beginning of a slot, abeginning of a half-slot, a beginning of a sub-slot, wherein a sub-slotcorresponds to a set of consecutive OFDM symbols and is based on aconfiguration of a timing relationship between different sets oftransmission opportunities for the PUCCH with HARQ-ACK feedback.
 17. Themethod of claim 14, wherein the K1 offset value indicates a time betweenan end of the scheduled PDSCH and an earliest start of the PUCCHcarrying the HARQ-ACK feedback, in units of slots, half-slots, orsub-slots, wherein a sub-slot corresponds to a set of consecutive OFDMsymbols and is based on a configuration of a timing relationship betweendifferent sets of transmission opportunities for the PUCCH with HARQ-ACKfeedback.
 18. The method of claim 13, the method further including:determining another PUCCH resource carrying UCI other than HARQ-ACKfeedback, and the scheduled PUSCH resource; determining whether at leastone of the another PUCCH resource and the scheduled PUSCH resourceoverlap in time with a determined PUCCH resource to carry HARQ-ACKfeedback; and determining, for transmission to the BS, one of: anupdated PUCCH resource carrying at least one bit of HARQ-ACK feedbackand the UCI other than HARQ-ACK feedback, or an updated PUSCH resourceto carry at least one bit of HAR-ACK feedback multiplexed with UplinkShared Channel (USCH) and another UCI other than the UCI.
 19. The methodof claim 18, wherein: the updated PUCCH resource is to carry a combinedUCI including information bits corresponding to respective ones of theHARQ-ACK feedbacks; and the method further includes: decoding a DownlinkControl Information (DCI) from the BS including a PUCCH resourceindicator (PRI) field; determining the updated PUCCH resource based onthe PRI field, the PRI field indicating a PUCCH resource carrying afirst or a last dynamic HARQ-ACK feedback of the one or more bits ofHARQ-ACK feedback; determining a PUCCH resource set based on a totalpayload size of the combined UCI; and selecting a PUCCH resource fromthe PUCCH resource set using the PRI.
 20. The method of claim 18,wherein the method further includes, in response to a determination thata plurality of PUCCH resources carrying dynamic or semi-persistentscheduled (SPS) HARQ-ACK feedbacks overlap with the scheduled PUSCHresource, and that the plurality of PUCCH resources and the scheduledPUSCH resource are from a same service type or priority, encodinginformation bits corresponding to respective ones of the HARQ-ACKfeedbacks onto the updated PUSCH resource.
 21. The method of claim 20,the method further including encoding and mapping information bitscorresponding to respective ones of the HARQ-ACK feedbacks into theupdated PUSCH resource separately, and to allocate an amount ofresources for each of the information bits corresponding to respectiveones of the HARQ-ACK feedbacks based on a payload size and a beta offsetof each of the information bits corresponding to respective ones of theHARQ-ACK feedbacks.
 22. The method of claim 20, the method furtherincluding concatenating the information bits corresponding to respectiveones of the HARQ-ACK feedbacks to multiplex information bitscorresponding to respective ones of the HARQ-ACK feedbacks into theupdated PUSCH resource.
 23. A device of a User Equipment (UE) the deviceincluding: means for determining that the UE is configured with afeature of multiple Physical Uplink Control Channel (PUCCH) resourceswith Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedbackwithin a slot; means for determining a Physical Uplink Control Channel(PUCCH) resource to carry HARQ-ACK feedback in response to a scheduledPhysical Downlink Shared Channel (PDSCH) resource; and encoding fortransmission to a base station (BS) the PUCCH resource, the PUCCHresource to carry the HARQ-ACK feedback and: another PUCCH resourcecarrying Uplink Control Information (UCI) other than HARQ-ACK feedback,and a scheduled Physical Uplink Shared Channel (PUSCH) resource.
 24. Thedevice of claim 23, further including: means for decoding a DownlinkControl Information (DCI) from the BS including a PUCCH resourceindicator (PRI) field; and means for determining the PUCCH resourcebased on the PRI and a K1 offset value, wherein the K1 offset value isbased on a Physical Downlink Shared Channel (PDSCH) resource to HARQtiming indicator (PDSCH-to-HARQ-timing-indicator) field in the DCIformat or on a higher layer parameter downlink data to uplinkacknowledgment (di-DataToUL-ACK) from the BS.
 25. (canceled)